@curusarn fair points. We haven't added configuring ports to the UI. Do you want to do that (and pass them in through ENV to Vector)?

We could do like OTEL_GRPC_PORT and OTEL_HTTP_PORT in all of install.sh, chart (exposed as otel_grpc_port and otel_http_port), and Vector, with Vector falling back to defaults

@curusarn fair points. We haven't added configuring ports to the UI. Do you want to do that (and pass them in through ENV to Vector)?

I feel strongly that they should be configured from a single place. Coordinating two places seems extra.

I thought is needs to be from helm chart values so that they are known at deploy time.
-> set something like "collectOtel.grpcPort", "collectOtel.httpPort" in helm chart values
-> this sets ENV in the container (easier if possible)
-> we either condition on that in Vector config or send it up to telemetry and generate appropriate vector config with otel source
-> we use the set ports automatically

I'm assuming we can't really set port in UI because the ports need to be set on the DaemonSet during deploy time. Or is there a way we can control this from UI fully?

I can't think of one, they need to be known at deploy time. Your plan sounds good, I'll do that 👍

Thank you! 🙏

@curusarn this should be much simpler - just take the values and forward into the container. The rest of the support goes into Telemetry.